Microsoft Training: Module 5: 80539 - Upgrade to Microsoft Dynamics CRM 2013
Make backups: Databases, custom code, configuration settings, etc.; Everything should be backed-up before upgrading
Prerequisites: CRM product license key; Verify system minimum requirements; Create an upgrade checklist using notes from this page and other sources; Uninstall SSRS data connector; If upgrading from CRM 4.0 you can use a trial version of CRM 2011 for the upgrade;
Upgrade approaches: Migration (recommended; separate hardware/environment); In-place (faster if it works; if fails need to reinstall CRM 2011 and restore database)
Upgrading is a one-way operation; Cannot upgrade from 4.0 to 2013; CRM 2011 must have rollup 6 or 14 (or later) before the upgrade
Migration approach: CRM to new server; If same SQL Server then upgrade occurs during installation; If new SQL Server then import the organization
Plug-ins and custom Workflow Activities:
Upgrade CRM 4.0 plug-ins: CRM 2013 does not support CRM 4.0 plug-ins nor 4.0 workflow activities. You need to revise the Visual Studio project and code in the plug-ins to work with the CRM 2013 SDK.
Any CRM 4.0 plug-ins registered to disk should be unregistered in the CRM 4.0 environment. Otherwise, after the upgrade to 2011 and 2013, you may not be able to unregister the plug-ins registered to disk. This may cause the definition of those legacy plug-ins to remain stuck in CRM and in the plug-in registration tool.
Client-side code:
Microsoft removed the "2007 endpoint" in CRM 2013. Upgrade code to use the 2011 endpoints.
Microsoft removed support for the CRM 4.0 form scripting objects. You'll need to update JavaScript code to use the Xrm.* objects.
Most unsupported JavaScript code (i.e., code that uses or manipulates the HTML DOM that CRM produces for forms, grids, etc.) will not work properly after the upgrade. Consider using supported means to carry the functionality forward, such as Xrm.Page code, business rules, HTML/JQuery web resources, workflows, dialogs, custom applications to run in an IFRAME, etc.
Use the Legacy Feature Check Tool and Custom Code Validation Tool to identify code that will not work in CRM 2013. See the tools page for links to these tools.
Running the Upgrade Application: The application runs several preliminary checks;
Database Table Merge: The database schema changed in CRM 2013 (ExtensionBase tables merged to a single entity table); Can delay this merge if needed
Hardware and Operating System Support: Unsupported: Windows XP, Office 2003, Exchange Server 2003, Exchange Server 2007 WebDAV protocol
Other necessary changes: Can no longer use the ISV folder for custom applications (must move to separate website); CRM 2011 SDK tool no longer required; Install CRM 2013 Reporting Extensions
Other recommended changes: Use out-of-box functionality where possible (reduce code, protect against future upgrades); Consider load-balancing, IFD
After the Upgrade:
Run the CRM 2013 Server Best Practices Analyzer tool
Upgrade forms: New forms are in place but deactivated by default; New forms have the same name as the entity (e.g., Account); You can merge in a previous form into the new form layout
Consider benefits of running "CRM monitoring service" and "Volume Shadow Service writer"
Upgrade Options